Dynamic voicemail receptionist system

ABSTRACT

A voicemail receptionist system includes a memory and a processor. The memory can store data relating to one or more users. An incoming communication can be handled by the voicemail receptionist system and provided with functionality based upon a user&#39;s preferences, for example. The data stored by the voicemail receptionist system can be updated at any time, or automatically updated upon updating of the data, or upon occurrence of a trigger event. Voicemail receptionist functionality can include standard voicemail system functionality as well as functionality relating to email, text messaging, MMS messaging, calendar features, schedule announcements, location data, as well as other features.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.12/053,525, filed Mar. 21, 2008, now allowed, which is a non-provisionalof and claims priority to U.S. Provisional Application No. 60/896,728,filed Mar. 23, 2007, each of which is hereby incorporated by referencein its entirety.

TECHNICAL FIELD

The present disclosure relates generally to voicemail platforms forcommunications devices. More particularly, the present disclosurerelates to a dynamic voicemail receptionist system for communicationsnetworks.

BACKGROUND

Voicemail is a popular telephone service feature, whether the telephoneis standard wired telephone service, wireless, e.g., cellular, telephoneservice, or even voice over internet protocol (VoIP). When a dialed linedoes not answer or is busy, a call can be handled by a voicemail system.A voicemail system often plays a recording for a calling party andprompts the calling party to leave a brief message, for example, aspoken message. The message is often recorded and stored until themessage is retrieved by a voicemail user.

Statistics suggest that there are close to 100 million cell phone usersin the United States. A recent trend in the U.S. includes replacingterrestrial telephone services with cellular telephone services, meaningthat a cellular telephone service may be a user's only telephone number.As such, voicemail, an almost standard feature for cellular telephoneservice, is relied upon by many users to report all missed telephonecalls. With the increased reliance upon cellular telephone service hascome a corresponding increased reliance upon other cellular telephonefeatures, for example, text messaging, which allows exchange of shortstrings of text between users without initiating a telephone call. Textmessages can be useful for delivering short messages that require noresponse from the message recipient, for example, “I'm on Flight 1234,arriving at 9:05 PM at Gate 1D.” As reliance upon cellular telephoneservices and voicemail increases, demand for enhanced voicemail serviceswill likely experience a corresponding increase.

SUMMARY

A voicemail receptionist system can include a memory configured to storeuser data associated with at least one user. The memory can also storeinstructions for handling a communication. The voicemail receptionistsystem can also include a processor operably connected to the memory.The processor is configured to determine how to handle a communicationbased upon the user data and the instructions stored in the memory. Theuser data can include any combination of data, including, but notlimited to, user preferences, calendar data, audio data, location data,network data, and device and/or account data. Instead of, or in additionto, using the user data, the voicemail receptionist system can alsoreceive data relating to an incoming call. The determination as to howto handle a communication can be based upon the incoming call data aswell as, or instead of, the user data. The voicemail receptionist systemcan also include a communications network interface. The communicationsnetwork interface can be a wireless and/or wired connection. If thevoicemail receptionist system resides on a mobile communications device,the communications network interface can include a device antenna.

A method for handling a call with a voicemail receptionist system caninclude obtaining user data associated with at least one user. The datacan be updated at any time. The voicemail receptionist system canreceive, from a calling party, a call for a user. The voicemailreceptionist system can analyze the user data and the data relating tothe received call to determine menu options for presentation to thecalling party. If there are menu options to present to the callingparty, the voicemail system can present the options to the callingparty. If there are no options to present to the calling party, thevoicemail receptionist system can provide standard voicemailfunctionality to the calling party, can terminate the call, or canforward the call to another node, platform, number, or the like. Acalling party can select a desired menu option. The voicemailreceptionist system can implement the selected option. If desired, thevoicemail receptionist system can validate the selected option prior toattempting to implement the option. In some embodiments, the selectedoption may require data that is not yet known by the voicemailreceptionist system. Alternatively, the selected option may be directedto dynamic information. The voicemail receptionist system can update anyinformation at any time, including after selection of a menu option, toimprove the accuracy of the information requested by the calling party.

In some embodiments, the method includes storing the obtained user datain a memory. In some embodiments, the menu options are provided as anaudio menu and the calling party can select an option using voicecommands and/or pressing a keypad button to send a DTMF tone to thevoicemail receptionist system. In some embodiments, the menu options arepresented by transmitting data to the calling party device withinstructions for formatting and displaying a menu to the calling party.When a calling party makes a selection, the voicemail receptionistsystem can receive data from the calling party device indicating themenu option selection.

The voicemail receptionist system can determine that an additionalselection is available after the first selection. The method cantherefore include presenting additional menu options to a calling partyand receiving an additional menu option selection from the callingparty. The received additional menu option can be executed by thevoicemail receptionist system, with or without validation by thevoicemail receptionist system of the first and/or additional menu optionselections. If the menu option selected is available, the voicemailreceptionist system can execute the selection. If the menu optionselected is not available, then menu options can be presented to thecalling party. The menu options can be new menu options or the same menuoptions already presented to the calling party.

A mobile device with a voicemail receptionist system can include amemory configured to store menu data associated with at least one menuoption. The memory can also be configured to store instructions forpresenting a menu. The device can also include a processor operablyconnected to the memory. The processor can be configured to determinehow to present, to a calling party, at least one menu option based uponthe instructions and the menu data. In some embodiments, the at leastone menu option is based upon user data associated with a called user.The menu options can include one or more of an option to send a textmessage, an option to send a voicemail message, an option to listen to aschedule associated with the called user, and an option to send contactinformation relating to the calling party to the called user. The userdata associated with a called user can be received over a communicationsnetwork.

These and additional features of the present disclosure will becomeapparent with reference to the attached drawings, wherein:

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 schematically illustrates an exemplary communications networkwith which the present disclosure can be implemented.

FIG. 2 schematically illustrates a voicemail receptionist systemaccording to an exemplary embodiment of the present disclosure.

FIG. 3 schematically illustrates a block diagram of an exemplary mobiledevice suitable for implementing an embodiment of the presentdisclosure.

FIG. 4 illustrates an exemplary graphical user interface for allowing auser to configure calendar data, according to an exemplary embodiment ofthe present disclosure.

FIG. 5 illustrates an exemplary graphical user interface for allowing auser to configure contact information, according to an exemplaryembodiment of the present disclosure.

FIG. 6 illustrates an exemplary graphical user interface for allowing auser to configure voicemail receptionist system preferences, accordingto an exemplary embodiment of the present disclosure.

FIG. 7 illustrates an exemplary graphical user interface for allowing auser to send an incoming call to a voicemail receptionist system,according to an exemplary embodiment of the present disclosure.

FIG. 8 illustrates an exemplary graphical user interface for allowing acalling party to interface with a voicemail receptionist system,according to an exemplary embodiment of the present disclosure.

FIG. 9 schematically illustrates a method for handling a communicationwith a voicemail receptionist system, according to an exemplaryembodiment of the present disclosure.

FIG. 10 illustrates an exemplary graphical user interface for providinga voicemail receptionist feature to a calling party, according to analternative embodiment of the present disclosure.

DESCRIPTION

As required, detailed embodiments of the present disclosure aredisclosed herein. It must be understood that the disclosed embodimentsare merely exemplary examples of the disclosure that may be embodied invarious and alternative forms, and combinations thereof. As used herein,the word “exemplary” is used expansively to refer to embodiments thatserve as an illustration, specimen, model or pattern. The figures arenot necessarily to scale and some features may be exaggerated orminimized to show details of particular components. In other instances,well-known components, systems, materials or methods have not beendescribed in detail in order to avoid obscuring the present disclosure.Therefore, specific structural and functional details disclosed hereinare not to be interpreted as limiting, but merely as a basis for theclaims and as a representative basis for teaching one skilled in the artto variously employ the present disclosure.

Referring now to the drawings in which like numerals represent likeelements throughout the several views, FIG. 1 schematically illustratesan exemplary communications network 10. The illustrated exemplarynetwork 10 includes a cellular network 12, the Internet 14, and a PSTN16. The cellular network 12 can include various components such as, butnot limited to, base transceiver stations (BTSs), mobile switchingcenters (MSCs), short message service centers (SMSCs), multimediamessaging service centers (MMSCs), home location registers (HLR5),charging platforms, traditional voicemail platforms, GPRS core networkcomponents, and the like. A mobile device 18, for example, a cellulartelephone, can be operatively connected to the cellular network 12. Byway of example, the cellular network 12 can be configured as a 2G GSM(Global System for Mobile communications) network and provide datacommunications via GPRS (General Packet Radio Service), and EDGE(Enhanced Data rates for GSM Evolution). By way of further example, thecellular network 12 can be configured as a 3G UMTS (Universal MobileTelecommunications System) network and provide data communications viathe HSPA (High-Speed Packet Access) protocol family, such as, HSDPA(High-Speed Downlink Packet Access), EUL (Enhanced Uplink) or otherwisetermed HSUPA (High-Speed Uplink Packet Access), and HSPA+ (EvolvedHSPA). The cellular network 12 is also compatible with future mobilecommunications standards including, but not limited to, pre-4G and 4G,for example. The illustrated cellular network 12 is shown incommunication with the Internet 14 and the PSTN 16, though it will beappreciated that this is not necessarily the case.

One or more Internet-capable devices, for example, a PC 20, a laptop 22,and a portable device 24, can communicate with one or more cellularnetworks 12, or even a device 18 connected thereto, through the Internet14. It will also be appreciated that the PC 20, the laptop 22, theportable device 24, or any other device, can communicate with theInternet 14 through the PSTN 16, the cellular network 12, or both. Asillustrated, a communications device 26, for example, a telephone, canbe in communication with the PSTN 16.

The cellular network 12 can include a wide array of nodes, devices,subsystems, networks, and subnetworks. For example, a cellular network12 can include one or more messaging systems or nodes, for example, ashort message service center (SMSC), a multimedia message service center(MMSC), voicemail systems, and the like. A cellular network 12 can alsoinclude various radios and nodes for passing voice, data, andcombinations thereof to and from radio transceivers, networks, and theInternet 14. As illustrated, a communications network 10 can include avoicemail receptionist system 30 (VMRS). The VMRS 30 can be hardware,software, and/or a combination thereof. While the VMRS 30 is illustratedas being in communication with the cellular network 12, it will beappreciated that the VMRS 30 can be hardware and/or software residing onthe cellular network 12, the PSTN 16, the portable device 18, theInternet 14, or a combination thereof, and can be accessible by and/orthrough multiple devices and networks. Furthermore, the VMRS 30 canreside on a private network accessible by the cellular network 12, thePSTN 16, or the Internet 14, or even the portable device 18. It shouldbe appreciated that substantially all of the functionality ascribed tothe communications network 10 can be performed by the cellular network12.

Turning now to FIG. 2, a schematic block diagram of an exemplary VMRS 30is illustrated according to an exemplary embodiment of the presentdisclosure. The illustrated VMRS 30 includes a communications networkinterface 32 that is operatively linked and in communication with aprocessor 34 via a data/memory bus 36. The communications networkinterface 32 allows the VMRS 30 to communicate with one or morecomponents of the communications network 10, or any device connectedthereto or residing thereon. It will be appreciated that if the VMRS 30resides on a device, for example, the device 18, that the communicationsnetwork interface 32 can be a communications component of the device,for example, a transceiver, receiver, transmitter, antennae, or acombination thereof. The processor 34 is operatively linked and incommunication with a memory 38 via a data/memory bus 36.

The word “memory,” as used herein to describe the memory 38,collectively refers to all memory types associated with the VMRS 30 suchas, but not limited to, processor registers, processor cache, randomaccess memory (RAM), other volatile memory forms, and non-volatile,semi-permanent or permanent memory types; for example, tape-based media,optical media, flash media, hard disks, combinations thereof, and thelike. While the memory 38 is illustrated as residing proximate theprocessor 34, it should be understood that the memory 38 can be aremotely accessed storage system, for example, a server on the Internet14. Moreover, the memory 38 is intended to encompass network memoryand/or other storage devices in wired or wireless communication with theVMRS 30, which may utilize the communications network interface 32 tofacilitate such communication. Thus, any of the data, applications,and/or software described below can be stored within the memory 38and/or accessed via network connections to other data processing systems(not shown) that may include a local area network (LAN), a metropolitanarea network (MAN), or a wide area network (WAN), for example.Accordingly, the present disclosure may operate on the VMRS 30, whereinthe VMRS 30 is configured as a server to one or more client dataprocessing systems as dictated by a client/server model.

The illustrated memory 38 can include other elements 40, for example,other data, software, instructions, applications, and the like, and avoicemail receptionist application 42 (VMRA). The illustrated memory 38can also include an operating system (not illustrated) and user data 44.

The user data 44 can include a number of categories of user data. Theuser data 44 can be associated with one or more users of the VMRS 30.Exemplary categories of user data 44 can include, for example, voicemailreceptionist preferences data 46, location data 48, calendar data 50,network data 52, audio data 54, account/device data 56, and other data(not illustrated). The user data 44 can be configured, stored, synced,updated, and deleted by any number of users, network operators, or otherauthorized parties. The user data 44 can be entered into any device,including, but not limited to, a device 18, a PC 20, a laptop 22, aportable device 24, or a server on the Internet 14. Additionally, or inthe alternative, the VMRS 30 can include functionality that enables auser to enter user data 44 directly into the VMRS memory 38.

Preferences data 46 can include the user's preferences for the VMRS 30.Preferences data 46 can include an indication as to which functions theuser wishes to make available to calling parties. For example, thepreferences data 46 can indicate whether the user wishes to sharelocation data, whether the user wishes to share calendar data, if theuser wishes to allow calling parties to send voicemail, text, or emailmessages, and if the user accepts contact information from callingparties. Other preferences are possible, including options for bypassingthe VMRS 30 and sending incoming calls for a user to another system,phone number, and/or user, forwarding numbers, voice or data deliveryoptions, including formats, size, delivery times, and the like, as wellas other preferences.

Location data 48 can include the user's location at any particular time.The location data 48 can be obtained from any suitable device or means,including, but not limited to, manual entry by the user of the user'slocation, from a presence indication provided by, for example, theuser's schedule, from the user's device, from a location server, or byusing GPS, cellular and/or Wi-Fi triangulation data, or the like todetermine the user's location. The location data 48 can be updatedconstantly, at predetermined intervals, by the user, or automatically,for example, when a call is received from a party with which the userwishes to share location data 48.

Calendar data 50 can include information relating to the user's calendarfor any time or time frame. For example, the calendar data 50 caninclude data indicating a user's appointments, free time, busy time,vacation time, and the like. As such, at any particular time, thecalendar data 50 can provide the VMRS 30 with data relating to theuser's calendar, or a portion thereof, which the VMRS 30 can pass to thecalling party. Additionally, or in the alternative, the calendar data 50can include a user's schedule for any time or time frame, which can bestored as data or even as an audio announcement providing detailsrelating to the user's schedule. In one embodiment, a user can record amessage conveying a schedule for a party, for example, the user'sschedule. In another embodiment, a software and/or hardware device orapplication can create an audio announcement that conveys a party'sschedule. If the calendar data 50 is an audio announcement, it can bestored as audio data 54.

Network data 52 can include data relating to the user's network, forexample, network configuration and protocols. The network data 52 canprovide any level of detail relating to the user's network. The networkdata 52 can be used to determine compatibility with a calling partydevice, network, and the like. The network data 52 can also detailrestricted and/or allowed networks, for example, cellular networks,roaming data, Wi-Fi hotspots, VPNs, and the like. Restricted and/orallowed networks can be set by a user, by a network provider, or by anyother authorized party. The network data 52 can be particularly usefulif the VMRS 30 resides on the device 18, since this can allow the device18 to format data or voice, for example, to enhance or optimizeperformance on the network.

Audio data 54 can include greetings, announcements, audio schedules,busy tones, ring tones, ringback tones, and the like. The audio data 54can be configured by the user, the network, the VMRS 30, or any otherauthorized party or device. In some embodiments, the user calendar data50 is converted to schedule announcements that are presented to acalling party as an audio file. In some embodiments, the user records aschedule announcement, for example, “I'm in the office today from 9:00AM to 5:00 PM . . . ” Greetings can also be tailored by the user or theVMRS 30 to indicate that a user is unavailable, or that the call hasotherwise been forwarded to a voicemail system or VMRS 30. Audio data 54can be stored in any desired format, including, but not limited to, WAV,AIFF, RAW, encoded in GSM CODEC, AAC, MP3, MP4, WMA, RA, MSV, DVF, andother open and proprietary audio formats.

Account/device data 56 can include data relating to the user's accountand/or device, including, but not limited to, the user's subscriptionplan and the user's device capabilities. For example, the VMRS 30 can bein communication with one or more billing platforms, subscriberdatabases, other network nodes, and the like, to receive theaccount/device data 56 relating to a user's subscription plan, usage,and billing information. Additionally, the account/device data 56 caninform the VMRS 30 of the features the user's device supports byindicating the IMEI, serial number, carrier, software version(s),firmware, carrier-specific applications, combinations thereof, or thelike. The account/device data 56 can pass-through the VMRS 30, or can bestored, at least temporarily. The VMRS 30 can use the account/devicedata 56 to determine what functionality should be provided to a callingparty based upon what types of data and/or voice the user's device 18can receive. If the user's device 18 does not support MMS messaging, forexample, then the option to send an MMS message to the user can bedisabled, if desired. Additionally, billing considerations can be usedto tailor options presented to a calling party. For example, if the userhas a 200 text message per month limit, then the VMRS 30 can, uponreceiving a notification from a billing platform, disable the ability tosend a text message through the VMRS 30 if the user has already exceededthe 200 text message per month limit when the call is sent to the VMRS30. Additionally, or in the alternative, a notification can be sent froma billing platform to the user, and the user can manually deactivate thetext message feature or override deactivation of the text messagefeature.

The VMRS 30 can identify any user data 44 as relating to a user, forexample by correlating a calling or called party with the user data 44.Correlated user data 44 can thereby identify a user's preferences,location, calendar, recordings, greetings, schedules, announcements,network configuration, connection protocols, presence, devicecapabilities and characteristics, billing plan, other information,combinations thereof, and the like. Correlation of user data 44 will bedescribed in more detail below with reference to FIG. 9.

FIG. 3 illustrates a schematic block diagram of an exemplary mobilecommunications device 18 for use in accordance with an exemplaryembodiment of the present disclosure. Although no connections are shownbetween the components illustrated in FIG. 3, the components caninteract with each other to carry out device functions.

As illustrated, the mobile communications device 18 can be a multimodehandset. FIG. 3 and the following discussion are intended to provide abrief, general description of a suitable environment in which thevarious aspects of an embodiment of the present disclosure can beimplemented. While the description includes a general context ofcomputer-executable instructions, the present disclosure can also beimplemented in combination with other program modules and/or as acombination of hardware and software. The term “applications” is usedherein, and can include routines, program modules, programs, components,data structures, and the like. Applications can be implemented onvarious system configurations, including single-processor ormultiprocessor systems, minicomputers, mainframe computers, personalcomputers, hand-held computing devices, microprocessor-based,programmable consumer electronics, combinations thereof, and the like.

The device 18 can include a variety of computer readable media,including volatile media, non-volatile media, removable media, andnon-removable media. Computer-readable media can include device storagemedia and communication media. Storage media can include volatile and/ornon-volatile, removable and/or non-removable media such as, for example,RAM, ROM, EEPROM, flash memory or other memory technology, CD ROM, DVD,or other optical disk storage, magnetic tape, magnetic disk storage orother magnetic storage devices, or any other medium that can be used tostore the desired information and that can be accessed by the device 18.

The device 18 can include a display 60 for displaying multimedia suchas, for example, text, images, video, telephony functions such as CallerID data, setup functions, menus, music, metadata, messages, wallpaper,graphics, internet content, device status, preferences settings, mapdata, location data, and the like. The device 18 can include a processor62 for controlling, and/or processing data. A memory 64 can interfacewith the processor 62 for the storage of data and/or applications 66. Anapplication 66 can include, for example, video player software,voicemail receptionist software, calendar software, music playersoftware, email software, messaging software, combinations thereof, andthe like. The application 66 can also include a user interface (UI)application 68. The UI application 68 can interface with a client 70(e.g., an operating system) to facilitate user interaction with devicefunctionality and data, for example, answering/initiating calls,entering/deleting data, configuring settings, address book manipulation,multimode interaction, and the like. The applications 66 can includeother applications 72 such as, for example, firmware, add-ons, plug-ins,voice recognition, call voice processing, voice recording, messaging,e-mail processing, video processing, image processing, music play,combinations thereof, and the like, as well as subsystems and/orcomponents. The applications 66 can be stored in the memory 64 and/or ina firmware 74, and can be executed by the processor 62. The firmware 74can also store code for execution during initialization of the device18.

A communications component 76 can interface with the processor 62 tofacilitate wired/wireless communications with external systemsincluding, for example, cellular networks, VoIP networks, LAN, WAN, MAN,PAN, that can be implemented using Wi-Fi, Wi-Max, combinations and/orimprovements thereof, and the like. The communications component 76 canalso include a multimode communications subsystem for providing cellularcommunications via different cellular technologies. For example, a firstcellular transceiver 78 can operate in one mode, for example, GSM, andan Nth transceiver 80 can operate in a different mode, for example UMTS.While only two transceivers 78, 80 are illustrated, it should beappreciated that a plurality of transceivers can be included. Thecommunications component 76 can also include a transceiver 82 forunlicensed communications using technology such as, for example, WI-FI,WI-MAX, BLUETOOTH, infrared, IRDA, NFC, RF, and the like. Thecommunications component 76 can also facilitate communications receptionfrom terrestrial radio networks, digital satellite radio networks,Internet-based radio services networks, combinations thereof, and thelike. The communications component 76 can process data from a networksuch as, for example, the Internet, a corporate intranet, a homebroadband network, and the like, via an ISP, DSL provider, or broadbandprovider.

An input/output (I/O) interface 84 can be provided for input/output ofdata and/or signals. The I/O interface 84 can be a hardwire connection,such as, for example, a USB, PS2, IEEE 1394, serial, parallel, Ethernet(RJ48), RJ11, and the like, and can accept other I/O devices such as,for example, a keyboard, keypad, mouse, interface tether, stylus pen,printer, thumb drive, touch screen, touch pad, trackball, joy stick,monitor, display, LCD, combinations thereof, and the like.

Audio capabilities can be provided by an audio I/O component 86 that caninclude a speaker for the output of audio signals and a microphone tocollect audio signals. The device 18 can include a slot interface 88 foraccommodating a subscriber identity system 90 such as, for example, aSIM or universal SIM (USIM). The subscriber identity system 90 insteadcan be manufactured into the device 18, thereby obviating the need for aslot interface 88. The device 18 can include an image capture andprocessing system 92. Photos and/or videos can be obtained via anassociated image capture subsystem of the image system 92, for example,a camera. The device 18 can also include a video component 94 forprocessing, recording, and/or transmitting video content.

A location component 96, can be included to send and/or receive signalssuch as, for example, GPS data, triangulation data, combinationsthereof, and the like. The device 18 can use the received data toidentify its location or can transmit data used by other devices todetermine the device 18 location. The device 18 can include a powersource 98 such as batteries and/or other power subsystem (AC or DC). Thepower source 98 can interface with an external power system or chargingequipment via a power I/O component 100.

Turning now to FIG. 4, a representative image from a VMR GUI 102 isillustrated according to an exemplary embodiment of the disclosure. Asillustrated, the GUI 102 can include device operational information 104,including, for example, a signal meter 106, an indication of the currentnetwork 108, the time of day 110, and a battery meter 112. Otherindicators, including, but not limited to, a short range radiocommunications device indicator, an alarm indicator, and the like, canbe included. In the illustrated GUI 102, a calendar 114 is currentlydisplayed. In the illustrated calendar 114, a desired date 116 ishighlighted, and associated action items 118 are listed below in thedetails section 120. In the illustrated details section 120, two items118 are listed for the desired date 116. The illustrated GUI 102 alsoincludes a menu portion 122, in which options relating to desired views,the date selection, and a new event creator, for example, are located.Additionally, the illustrated GUI 102 includes an option 124 forselecting whether the user's calendar data 50 will be shared with theVMRA 42.

Another exemplary GUI 102 image is illustrated in FIG. 5. In FIG. 5,exemplary contact information 126 associated with an exemplary contactis shown. In the illustrated exemplary GUI 102, the menu portion 122includes an option to edit the contact information, and an option toreturn to the entire contact list. Some device interfaces allow a userto enter many details relating to any particular contact. In theillustrated GUI 102, the illustrated contact information 126 includestwo telephone number fields 132, a ringtone designation field 134, anemail address field 136, and a physical address field 138. Theillustrated contact information 126 also includes an option 124 forselecting whether the contact designated by the contact information 126will be able to access the user's shared user data 44.

Another exemplary GUI 102 image is illustrated in FIG. 6. In FIG. 6, aVMR preferences interface 140 is illustrated. In the illustratedexemplary GUI 102, various options relating to the user's VMR user data44 can be provided to a user for customization. For example, theillustrated preferences interface 140 allows a user to toggle variousoptions, including a master toggle 142 for toggling on or off the VMRSfunctionality, a toggle 144 for toggling on or off acceptance ofvoicemail messages through the VMRS 30, a toggle 146 for toggling on oroff acceptance of email messages through the VMRS 30, a toggle 148 fortoggling on or off acceptance of SMS messages through the VMRS 30, atoggle 150 for toggling on or off acceptance of calling party contactinformation through the VMRS 30, a toggle 152 for toggling on or off theshare schedule feature of the VMRS 30, a toggle 154 for toggling on oroff the share calendar feature of the VMRS 30, a toggle 156 for togglingon or off the share location feature of the VMRS 30, a toggle 158 fortoggling on or off the bypass to voicemail feature of the VMRS 30, and atoggle 160 for enabling or disabling the feature for customizing VMRsettings to specific contacts in the user's contact list. Other options,for example, enabling realtime monitoring of VMRS 30 activity, enablingvideo messaging, enabling forwarding to websites, enabling busy phoneredial, enabling calling party hold, and the like, are contemplated, butare not illustrated for the sake of brevity.

In the illustrated preferences interface 140, acceptance of SMS messages148, location sharing 156, and the bypass option 158 are illustrated astoggled to “off.” All other options of the VMR application areillustrated as toggled to “on.” It will be appreciated that some usersmay wish to toggle certain features of the VMR application on or off.For example, some users are limited to a certain number of SMS messagesper billing cycle, after which a fee applies to each transmitted orreceived SMS message. These and other considerations may prompt someusers to toggle “off” the SMS acceptance option 148, as illustrated inFIG. 6. Additionally, or in the alternative, the SMS acceptance option148, and/or other options, can be automatically adjusted upon receipt ofaccount status indicating that use of some service or option is nearingthe capacity paid for, e.g., obtaining data usage, call time, textmessage counts, and the like, using STAR SERVICE. Furthermore, privacyconcerns or other issues may prompt some users to disable the sharelocation feature 152 of the VMRS 30. In one embodiment, a user candisable the share location feature 152 of the VMRS 30 for all anonymouscalls, and/or for particular contacts, numbers, locations, and the like.Various concerns and or motivations can inform the decisions made by theuser in choosing whether to toggle on or off any or all availableoptions of the VMRS 30.

Turning now to FIG. 7, a representative called-party view of a callstatus GUI 102 is illustrated according to an exemplary embodiment ofthe present disclosure. The illustrated GUI 102 includes a device statussection 104, a calling party information section 162, a calling partyrepresentative graphic 164, and a menu section 166. The illustrated menu166 includes an option 168 to answer the incoming call, an option 170 todecline the incoming call, and an option 172 to send the call to theVMRS 30. If the user selects the option 168 to answer the incoming call,the call can be connected with the device. If the user selects theoption 170 to decline the incoming call, the call can be handledaccording to device preferences. For example, some devices include adecline command, or substantially equivalent functionality, whereby thecall is handled as if the call is not answered. In the case of a devicewith VMRS support, the call can be forwarded to a standard voicemailsystem, terminated, provided with a busy signal, forwarded to adifferent telephone number, passed to a paging system, or forwarded to aVMRS 30, depending upon preferences set by the user, the device, thenetwork, or another authorized party. If the user selects the option 172to send the call to the VMRS 30, the call can be sent to the VMRS 30 andhandled according to the user's user data 44 and the calling party data,as explained above with reference to FIG. 2.

Turning now to FIG. 8, a representative calling-party view of avoicemail receptionist GUI 102 is illustrated according to an exemplaryembodiment of the present disclosure. The illustrated GUI 102 includes adevice status section 104, and a call status section 176. The callstatus section 176 can provide the user of the device with information,for example, information relating to a present communication. In theillustrated embodiment, the call status section 176 indicates to theuser that the called party is unavailable, and that the call has beenforwarded to a VMRS 30. As explained above with reference to FIG. 7, acalled party may be unavailable for many reasons, for example, theringer is turned off or broken, in which case the user does not knowthat a call has been received, the user and the user's device may be outof communication range or busy. Similarly, the user may be using thedevice when the call is received, may decline the call, may send thecall to the receptionist, or may not pick up the call for anotherreason. Regardless of the reason for the call being forwarded to theVMRS 30, as will be explained in detail below, the VMRS 30 can forwardto the calling party device options for displaying to a user in a menu178. In the illustrated embodiment, the user can choose to send avoicemail message 180, send an email message 182, send an SMS message184, send contact information 186, view the user's calendar 188, listento the user's schedule 190, view the user's current location 192, or endthe current call 194. Some or all of the options on the menu 178 caninclude a submenu, access to which can be gained by pressing orselecting the submenu selection option 196. For example, the illustrated“View Calendar” option 188 includes a submenu selection option 196. Whenthe submenu selection option 196 is selected by a calling party, a newsubmenu can be presented to the calling party. The submenu can includean option to select a specific view, e.g., a day, week, or month, or toshow certain types of time, e.g., free time, time at work, and the like.A configured calendar can be presented to the calling party inaccordance with selected options or default options. Additional optionscan be presented with the menu, for example, an option to leave a voicemessage, send a text message, view location, and the like, can beprovided to a calling party since such functionality can be useful oncea user's calendar has been viewed. Additionally, or in the alternative,the submenu can present a calendar with various options without the needfor configuring the presented view. Other options can also includesubmenus, and the submenus can be presented using audio menus instead ofthe illustrated graphical user interface.

Turning now to FIG. 9, an exemplary method 200 for handling an incomingcommunication at a VMRS 30 is illustrated. It should be understood thatthe steps described are not necessarily presented in any particularorder and performance of some or all the steps in an alternativeorder(s) is possible and is contemplated. The steps have been presentedin the demonstrated order for ease of description and illustration.Steps can be added, omitted and/or performed simultaneously withoutdeparting from the scope of the appended claims. Additionally, it shouldbe appreciated that a phone call can end at any time for a number orreasons. As such, there is no requirement that the method 200 beperformed in its entirety. Some or all steps of this process, and/orsubstantially equivalent steps, can be performed by execution ofcomputer-readable instructions included on a computer readable medium.Furthermore, it must be understood that the word “handle,” and allvariants thereof, as used in the description and in the claims, refersto the determination and/or implementation, by the VMRS 30, of whatfunctionality to provide a calling party, how to implement thatfunctionality, and what information the determination is based upon.

The illustrated method 200 begins and flows to block 202, wherein theVMRS 30 obtains user data 44 relating to a user of the VMRS 30. The userdata 44 can be obtained in a number of ways. For example, in someembodiments, user data 44 is configured on a mobile device 18 and“pulled” or “pushed” to the VMRS 30 from the device 18 by a networkcomponent. For example, a user can customize an application on thedevice, on the web, or on a sync device such as a PC, for example.Application data can be synced with the mobile device and “pulled” or“pushed” from the device. Alternatively, data can be synced with theVMRS 30 by a node on the Internet 14, by a sync device, or any otherappropriate device. A “pull” operation, as used herein, can include aquery from the network to the device for new data, and the transmissionfrom the device to the network of the data. In other embodiments, userdata 44 is configured via an input interface, for example, a PC 20,laptop 22, or portable device 24 in operable connection with theInternet 14, or a mobile device 18 in operable connection with theInternet 14 via a network, e.g., the cellular network 12. In otherembodiments, user data 44 is configured and “pushed” to the network 12by the user or the user's device. A “push” operation, as used herein,includes a device 18 transmitting data to the network. A “push”operation can be initiated by a user, scheduled by the user or device,or can automatically occur when data is updated, for example.

Regardless of how the user data 44 is obtained by the VMRS 30, the userdata can be stored in a VMRS memory 38, as shown at block 204. Asillustrated by block 206, the user data 44 stored in the VMRS memory 38can be updated at any time, for example, by a sync operation similar tothe sync operation described above. For example, the user data 44 can beupdated periodically, on demand, upon changes, or based upon any desiredinterval or trigger event. In still other embodiments, user data 44 canbe updated periodically by syncing the user data 44 with one or moreuser devices. Any changes to the user data 44 can be saved in the VMRSmemory 38, as illustrated at block 204. It will be appreciated that theexchange, saving, and/or updating of user data 44 can occur many timesbefore the illustrated method flows to the next block. In someembodiments, block 206 corresponds to a starting position for the method200, and blocks 202-204 correspond to a VMRS setup method.

At any time, as shown in block 208, the VMRS 30 can receive a call for auser. Although the process for delivering a call to the VMRS 30 will notbe described in detail, it should be appreciated that a call can beforwarded to the VMRS 30 by a network node when the called party doesnot answer, for example. Alternatively, the VMRS 30 can effectivelyintercept all calls by configuring the network to deliver all callsdirectly to the VMRS 30. Alternatively, the device can forward calls tothe VMRS 30, for example, by using a call forward feature. Regardless ofhow a call arrives at the VMRS 30, the calling party's call data canalso be delivered to the VMRS 30.

As illustrated in block 210, the VMRS 30 can use the user data 44 forthe called party, and the call data to retrieve various data from theVMRS memory 38, a network node, and/or the Internet 14. For example, theVMRS 30 can retrieve data relating to the user's, i.e., the calledparty's, general preferences, greetings, announcements, schedule,calendar data, network data, location data, and the like. Furthermore,the VMRS 30 can correlate the call data relating to the calling party tothe user data 44, whereby any specific preferences relating to thecalling party can be retrieved. For example, if a user has blockedcertain data from being accessible by a calling party, the VMRS 30 candetermine this user preference by correlating the call data and the userdata, for example. It should be noted that portions of data can beretrieved at various times, depending upon how the VMRS 30 isimplemented by any particular user, network, provider, or the like. Forexample, the VMRS 30 may first determine what menu options should beprovided before retrieving data relating thereto. Additionally, or inthe alternative, the VMRS 30 can determine that a calling party cannotoperate a data session, in which case the VMRS 30 will only need to getdata for a voice-driven embodiment of the VMRS 30.

In block 212 of the illustrated method 200, the VMRS 30 uses theretrieved user data 44, and any correlations between the user data 44and the call data, to generate menu options for the calling party. Forexample, if the user has decided to share his or her calendar data 50with calling parties, the VMRS 30 can include a “View Calendar” optionin the list of menu options. The calling party can have access to the“View Calendar” option, for example, as a graphical menu choice, asillustrated by the option 188 in FIG. 8. If the user has decided toshare location data 48, the VMRS 30 can add a “View Current Location”option to the list of options, and provide the calling party with anoption to “View Current Location,” as illustrated by the option 192 inFIG. 8. Similarly, if a user has decided to allow text messages to besent from the VMRS 30, then the VMRS 30 can include a menu option tosend a text message, as illustrated by the option 184 in FIG. 8. Similardecisions can be made relating to each possible menu option and whetheror not to include each possible menu option.

At block 214, the VMRS 30 can determine if there are any optionsavailable for the calling party. In some instances, the VMRS 30 candetermine that no data is to be shared with the calling party. Forexample, a user may decide to block the calling party from accessing anyfunctionality of the VMRS 30 relating to the user. Alternatively, theuser may not have updated the VMRS 30 with any user data 44. Regardlessof why there are no menu options, the VMRS 30 can play the user'sgreeting and record a voicemail message, as illustrated in block 216.Alternatively, if there is no VMRS functionality needed, the call can beforwarded to a standard voicemail system to remove unnecessary datatransfer from the VMRS 30. After the call is forwarded out of the VMRSnetwork, handled by the VMRS 30, or handled by a standard voicemailsystem, the method 200 can end. It will also be appreciated that a usercan disable the accept voicemail messages option for a particularcalling party, or for all calling parties. Accordingly, if there are noavailable options for a calling party, the method can simply end withoutany other action, though a recording can be played for the callingparty, if desired.

Returning now to decision block 214, if the VMRS 30 determines thatthere are menu options available, the method can proceed to block 218,wherein the VMRS 30 determines if the VMR functionality should be sentto the device using a data connection, a voice connection, or both. Auser may prefer using a data connection, a voice connection, or both.For example, sending data to a device to enable a user to view acalled-party's calendar may require the receipt of packet data at acalling party's device. If the calling party's device does not supportsimultaneous voice and data communication, for example, the voicecommunication can be terminated and a data session can be opened toenable the device to use the data-based functionality of the VMRS 30.Additionally, a user may prefer utilizing a data session for some or allof the VMRS functionality due to billing considerations, or to use extraor enhanced features for a GUI, for example. In any case, the VMRS 30can inform a user, or the user's device, that a data session can becommenced to use some or all functionality of the VMRS 30. In someembodiments, the data session can be almost immediately opened so thereappears to be little, if any, perceived delay between terminating thevoice communication and opening the data communication. Additionally,the VMRS 30 can operate as a feature that is delivered to a mobiledevice 18 exclusively through a data session. In such an embodiment, therecordings, greetings, announcements, and the like, can be provided to acalling party as streaming audio or video. Some or all data can becached in a calling party device and updated only as needed. Such anembodiment may have particular usefulness for users with unlimited dataplans and/or the inability to open simultaneous voice and data sessions.In any embodiment, voice and/or data usage can be billed on a post-paidor a pre-paid basis, or all VMRS functionality can be delivered to adevice as a bundled package.

Aside from a user's preferences, the decision whether to use data,voice, or both to deliver VMRS functionality can be based on a number offactors. For example, the VMRS 30 may determine that the calling partycan open a data session while the call is active. In such a case, theVMRS 30 can send some or all of the VMR functionality using a dataconnection, as represented by block 220 a. It will be appreciated thatit may be desirable to deliver some or all of the VMRS functionalityusing a voice connection instead of, or in addition to, the dataconnection. For example, the VMRS 30 may determine that the devicecannot use data while on a voice call. In such a case, the VMRS 30 canuse a voice/keypad driven menu system, as illustrated at block 220 b, orcan instruct the device to terminate the call and initiate a datasession. For example, if the calling party is using a mobile device, thecellular network 12 can use known data to determine if a data session isavailable. The known data can include, but is not limited to, thenetwork with which the mobile device is registered, the IMEI of thedevice, the user's subscription or service plan, or other known orascertainable data. If the calling party device is not a mobile device,the VMRS 30 can use the calling party's call data, e.g., the phonenumber or IP address of the calling party, to determine if the callingparty device supports data and/or voice transfer. If the calling partydevice does not support data transfer, or if the VMRS 30 is unable todetermine if the calling party device supports data transfer, the method200 can flow to block 220 b, wherein the VMRS functionality can beprovided using recordings and user input via voice and/or keypad DTMFtones.

As illustrated in block 220 b, the VMRS 30, can play a user's greetings,announcements, or the like, and can play a menu for the calling partythat includes one or more options selectable by a voice command, a DTMFtone, or the like, e.g., “press or say ‘1’ to leave a message, press orsay ‘2’ to send a text message, press or say ‘3’ to hear the user'sschedule,” and the like. The VMRS 30 can wait for a response from thecalling party, as illustrated in block 222.

Although the illustrated method 200 shows block 222 occurring after 220a, it will be appreciated that some menu systems allow a user to input acommand to choose a menu option at any time within a menu, and that somesystems restrict a user from choosing a menu option until all menuoptions have been played. It will be appreciated that these and otherpossibilities are not easily illustrated simultaneously, but areincluded in the scope of the appended claims.

Returning now to the decision block 218, if the VMRS 30 determines thatthe calling party device can support data transfer the method 200 flowsto block 220 a. In block 220 a, the VMRS 30 can format and send acommand to the calling party device to display the VMRS menu. Thecommand to display the VMRS menu can include a list of the options to bedisplayed to the calling party. The command will be understood by thecalling party's device, and/or a VMR application residing on the device,and can be used to command the calling party device to display an optionmenu, an example of which is illustrated in FIG. 8 above. The method 200can flow to block 222, wherein the VMRS 30 waits for a response from thecalling party.

As illustrated in block 224, the VMRS 30 can receive a response from thecalling party. As explained above, the calling party's response can betransferred to the VMRS 30 over one or more data connections, one ormore voice connections, or both. As illustrated at block 226, the VMRS30 can examine the response received and validate the response todetermine if the response entered corresponds to a choice offered to thecalling party and/or if the data needed to execute the response isavailable. If the response entered by the calling party is executable,the method 200 can flow to block 228. If the response entered by thecalling party does not correspond to an available option, or if the datais not available, the method 200 can return to block 220 a or 220 b, asillustrated. It will be appreciated that while the process flows back toblock 220 a or 220 b, the VMRS 30 can inform the calling party that theresponse entered is not available and/or can generate a new menu topresent to the calling party (neither of which are illustrated).

As illustrated in block 228, the VMRS 30 can execute a validatedresponse. It will be appreciated that the validation described abovewith respect to block 226 can occur during or after attempted executionof the received response. Execution of the response can include a numberof routines, subroutines, and/or actions taken by a number of servers,nodes, applications, programs, and the like. For example, if the callingparty is communicating with the VMRS 30 over a voice connection, thenselection by the calling party of the “Send a Text Message” can requireentry by the calling party of a message in numeric or alpha-numericcharacters using, for example, a telephone keypad or voice commands. Inone embodiment, the calling party can record a spoken message and theVMRS 30 can convert the spoken message to text using a voice to textapplication. The converted message can be spoken back to the callingparty to ensure the message was recorded correctly. Additionally, or inthe alternative, a calling party can send a text message using, forexample, the telephone keypad to spell the words of the message. Similarverification can be used to ensure the message is taken correctly.Additionally, or in the alternative, the text message can include aphone number entered, for example, using the telephone keypad or voicecommands. A recorded message can also be sent to the user as an audiofile that is embedded or attached to an email or MMS message. If theuser selects the “View Current Location” option, the VMRS 30 can providelocation information. The location information can be queried from, forexample, the user's device, a location server, or using triangulation,for example. The location information can be obtained at any time, orcan be updated when the option is selected. Other selected options canrequire other actions taken by the VMRS 30. For example, selecting anoption to leave a voicemail message can require playing a recordedgreeting or announcement for the calling party. Requesting the “Listento Schedule” option can include querying the user's device, obtainingthe user's calendar data 50, or retrieving a schedule recording. Otheroptions can prompt the VMRS 30 to take other actions, though notdescribed here in detail. The method 200 can flow to block 230.

As illustrated in block 230, the VMRS 30 can determine if anotherresponse is possible. For example, if the calling party chooses to viewthe user's calendar, listen to the user's schedule, or view currentlocation, the VMRS 30 may be able to accept a second response afterexecuting the first response. The calling party may determine, afterlistening to a schedule or viewing a calendar, that a message should orshould not be left for the user. The VMRS 30 can provide such options tothe calling party, if desired, and can, therefore, accept a second orother additional response. If the VMRS 30 determines that no secondresponse is possible, the call can be ended and the method 200 can end.If the VMRS 30 determines that a second response is possible, the method200 can flow to block 232, wherein the VMRS 30 can configure a secondmenu and return to block 222 to wait for a second response from thecalling party. Steps 220 a-232 can be iterated until no further responseis available or entered by the calling party. When there is no secondresponse available or entered by a calling party, the method 200 ends.

It should be appreciated that a call being handled by the VMRS 30 can bemoved, at any time, from and between one or more voice connections toone or more data connections, or combinations thereof. It should also beappreciated that a call being handled by the VMRS 30 can be ended at anytime, for example, by a calling party terminating the call or the callbeing terminated. A call can be terminated purposefully, orinadvertently, for example, by leaving a coverage area, losing power ata device, and the like. In any case, the method 200 is exemplary onlyand need not be completed for any particular communication.

Turning now to FIG. 10, a graphical user interface for providing acalling party with a voicemail receptionist feature is illustrated,according to an alternative embodiment of the present disclosure. Asshown, a device 18 includes a display 60. The display 60 is currentlydisplaying a GUI 102 for providing the calling party with VMRSfunctionality. The GUI 102 includes a call status section 176 and a menusection 178, similar to the GUI 102 illustrated in FIG. 8. The menusection 178 includes an option 180 to send a voicemail message, anoption 182 to send an email message, an option 190 to listen to theuser's schedule, and an option 186 to send contact information to theuser. It will be appreciated that the contact information can beassociated with any party, including, but not limited to, the callingparty. The illustrated device 18 includes a selector switch 240 and softkeys 242, 244 for selecting the desired option 180, 182, 186, 190.

While the foregoing description has described the VMRS 30 as residing asan application on a communications network 10 and as software on adevice 18, it will be appreciated that, as mentioned above, a device 18can include the user data and the VMRA 42, both of which can reside in amemory of the device 18. As such, two devices with VMR support can “talkto each other” to provide the functionality needed for the VMRS 30. Itwill be appreciated that this embodiment can provide benefits to theuser, but that this embodiment can also require more data and/or voiceusage by the called party device 18. User preferences can be used todetermine whether the VMRS 30 functionality should be employed at thedevice 18 or at the communications network 10.

It must be understood that the illustrated GUIs are exemplary only andother contemplated user interfaces, screen layouts, selection methods,and the like are contemplated, including an embodiment of the VMRS 30that does not provide a GUI at the user's device, the calling party'sdevice, or either device. Furthermore, a selection can be made usingvarious embodiments of softkeys and/or key selections on a mobile orstationary telephone keypad, for example, and is not limited to theillustrated GUI. Additional and/or alternative selector switches andjoysticks can be used to select a desired option or icon correspondingto a desired option. Input methods can also include touch screens orvoice commands. Any desired screen layout or format can be used,including plain text and icons, for example.

The law does not require and it is economically prohibitive toillustrate and teach every possible embodiment of the present claims.Hence, the above-described embodiments are merely exemplaryillustrations of implementations set forth for a clear understanding ofthe principles of the disclosure. Variations, modifications, andcombinations may be made to the above-described embodiments withoutdeparting from the scope of the claims. All such variations,modifications, and combinations are included herein by the scope of thisdisclosure and the following claims.

What is claimed is:
 1. A method comprising: receiving, by a servercomprising a processor, a communication from a wireless communicationsdevice associated with a calling party, the communication directed to auser; retrieving, by the processor, user data associated with the user;generating, by the processor, a first menu option for the calling partybased on the user data associated with the user, wherein the first menuoption allows the calling party to listen to calendar data associatedwith the user, and wherein the calendar data comprises data indicatingat least one of an appointment associated with the user, free timeassociated with the user, busy time associated with the user, orvacation time associated with the user; transmitting, by the servercomprising the processor, the first menu option to the wirelesscommunications device associated with the calling party; receiving, bythe server comprising the processor, a response from the calling party;determining, by the server comprising the processor, whether theresponse from the calling party corresponds to the first menu optiontransmitted to the wireless communications device associated with thecalling party; and if the response does not correspond to the first menuoption transmitted to the wireless communications device associated withthe calling party, informing, by the server comprising the processor,the calling party that the response is unavailable.
 2. The method ofclaim 1, wherein the user data comprises user preferences and thecalendar data, and wherein at least a portion of the calendar data isprovided to the calling party in response to a selection of the firstmenu option.
 3. The method of claim 1, further comprising generating asecond menu option allowing the calling party to access location dataassociated with the user, wherein at least a portion of the locationdata is provided to the calling party in response to a selection of thesecond menu option.
 4. The method of claim 1, wherein the communicationfrom the calling party to the user is a voice communication, and whereinthe method further comprises: receiving call data associated with thecalling party; determining, based on the call data associated with thecalling party, that the wireless communications device associated withthe calling party does not support simultaneous voice and datacommunications; and in response to determining that the wirelesscommunications device associated with the calling party does not supportsimultaneous voice and data communications, terminating the voicecommunication, initiating a data session with the wirelesscommunications device of the calling party, and transmitting the firstmenu option to the wireless communications device of the calling partyusing the data session.
 5. The method of claim 1, further comprisinggenerating a second menu option allowing the calling party to providecontact information associated with the calling party to the user. 6.The method of claim 1, further comprising generating a second menuoption allowing the calling party to send a voicemail message to theuser, a third menu option allowing the calling party to send an emailmessage to the user, and a fourth menu option allowing the calling partyto send a short message service message to the user.
 7. A systemcomprising: a processor; and a memory that stores instructions that,when executed by the processor, cause the processor to performoperations comprising: retrieving, in response to receiving acommunication from a wireless communications device associated with acalling party directed to a user, user data associated with the user,generating a first menu option for the calling party based on the userdata associated with the user, wherein the first menu option allows thecalling party to listen to calendar data associated with the user, andwherein the calendar data comprises data indicating at least one of anappointment associated with the user, free time associated with theuser, busy time associated with the user, or vacation time associatedwith the user, transmitting the first menu option to the wirelesscommunications device associated with the calling party for display atthe wireless communications device, receiving a response from thecalling party, determining whether the response from the calling partycorresponds to the first menu option transmitted to the wirelesscommunications device associated with the calling party, if the responsedoes not correspond to the first menu option transmitted to the wirelesscommunications device associated with the calling party, informing thecalling party that the response is unavailable, and if the response doescorrespond to the first menu option, executing the response.
 8. Thesystem of claim 7, wherein the user data comprises user preferences andthe calendar data, and wherein at least a portion of the calendar datais provided to the calling party in response to a selection of the firstmenu option.
 9. The system of claim 7, wherein the operations furthercomprise generating a second menu option allowing the calling party toaccess location data associated with the user, wherein at least aportion of the location data is provided to the calling party inresponse to a selection of the second menu option.
 10. The system ofclaim 7, wherein the communication from the calling party to the user isa voice communication, and wherein the operations further comprise:receiving call data associated with the calling party; determining,based on the call data associated with the calling party, that thewireless communications device associated with the calling party doesnot support simultaneous voice and data communications; and in responseto determining that the wireless communications device associated withthe calling party does not support simultaneous voice and datacommunications, terminating the voice communication, initiating a datasession with the wireless communications device of the calling party,and transmitting the first menu option to the wireless communicationsdevice of the calling party using the data session.
 11. The system ofclaim 7, wherein the operations further comprise generating a secondmenu option allowing the calling party to provide contact informationassociated with the calling party to the user.
 12. The system of claim7, wherein the operations further comprise generating a second menuoption allowing the calling party to send a voicemail message to theuser, a third menu option allowing the calling party to send an emailmessage to the user, and a fourth menu option allowing the calling partyto send a short message service message to the user.
 13. Anon-transitory computer-readable storage device storing instructionsthat, when executed by a processor, cause the processor to performoperations comprising: retrieving, in response to receiving acommunication from a wireless communications device associated with acalling party to a user, user data associated with the user; generatinga first menu option for the calling party based on the user dataassociated with the user, wherein the first menu option allows thecalling party to listen to calendar data associated with the user, andwherein the calendar data comprises data indicating at least one of anappointment associated with the user, free time associated with theuser, busy time associated with the user, or vacation time associatedwith the user; transmitting the first menu option to the wirelesscommunications device associated with the calling party for display atthe wireless communications device; receiving a response from thecalling party; determining whether the response from the calling partycorresponds to the first menu option transmitted to the wirelesscommunications device associated with the calling party; if the responsedoes not correspond to the first menu option transmitted to the wirelesscommunications device associated with the calling party, informing thecalling party that the response is unavailable; and if the response doescorrespond to the first menu option, executing the response.
 14. Thenon-transitory computer-readable storage device of claim 13, wherein theuser data comprises user preferences and the calendar data, and whereinat least a portion of the calendar data is provided to the calling partyin response to a selection of the first menu option.
 15. Thenon-transitory computer-readable storage device of claim 13, wherein theoperations further comprise generating a second menu option allowing thecalling party to access location data associated with the user, whereinat least a portion of the location data is provided to the calling partyin response to a selection of the second menu option.